docs(mobile): fix kilo run launch command and switch orchestrator to sonnet-5 high#4601
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummarySecond commit switches the orchestrator launch command's model from Files Reviewed (1 files)
Previous Review Summary (commit 447eff2)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 447eff2)Status: No Issues Found | Recommendation: Merge Executive SummaryDocumentation-only reordering of the Files Reviewed (1 files)
Reviewed by claude-sonnet-5 · Input: 16 · Output: 2.2K · Cached: 288.8K Review guidance: REVIEW.md from base branch |
iscekic
changed the title
3 participants
Two fixes to the orchestrator launch command in
MOBILE_WORKFLOW.md:Argument order:
kilo run --file <handoff> "<message>"fails withFile not found: <message>because--fileis an array option that consumes the trailing positional (reproduced on kilo 7.4.9). The message now comes before the flags, with a note explaining why.Orchestrator model:
kilo/kilo-auto/frontiercurrently gets zero prompt caching through the gateway (verified: 2-turn probe, both turns billed full input, ~$5.2/M blended; 351M input tokens across last night's orchestrator sessions billed uncached at ~$1,800).kilo/anthropic/claude-sonnet-5 --variant highcaches correctly (verified: turn 1 cache-write 40k, turn 2 cache-read 39.9k, 12x cheaper), so the workflow now launches orchestrators on it until frontier caching is fixed.